home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20041116-20060924
/
000186_joe.powell@lmco.com_Mon Oct 31 16:19:26 2005.msg
< prev
next >
Wrap
Internet Message Format
|
2006-09-27
|
3KB
Path: newsmaster.cc.columbia.edu!panix!newsfeed-00.mathworks.com!newscon06.news.prodigy.com!prodigy.net!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!g43g2000cwa.googlegroups.com!not-for-mail
From: joe.powell@lmco.com
Newsgroups: comp.protocols.kermit.misc
Subject: Why am I doing undesired SSL authentication?
Date: 31 Oct 2005 13:05:53 -0800
Organization: http://groups.google.com
Lines: 36
Message-ID: <1130792753.825104.9270@g43g2000cwa.googlegroups.com>
NNTP-Posting-Host: 192.91.147.34
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1130792759 3352 127.0.0.1 (31 Oct 2005 21:05:59 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 31 Oct 2005 21:05:59 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 MVNPX1
Complaints-To: groups-abuse@google.com
Injection-Info: g43g2000cwa.googlegroups.com; posting-host=192.91.147.34;
posting-account=xgv93Q0AAADzqtbiPG1PAX2w9BlmAlpA
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15432
In May, greatly due to this group's influence, I developed an
application on a SUSE 8 platform using the FTP client built in Kermit
7. This app's only viable method for logging in to a remote server is
with a userid and password, i.e. no SSL, Kerberos, etc.. It worked very
well.
We recently switched to a new server which included upgrading from SUSE
8 to SUSE 9 and from cKermit 7 to cKermit 8. After this switch, Kermit
now tries to perform SSL authentication before each session which fails
because we do not (and never will) have this set up with the servers to
which we are connecting.
Kermit docs show that it bases its default authentication settings on
which libraries exist when it is installed. From this and our new
attempts at SSL authentication, it seems some SSL library(ies) exist on
our new server that were not on our old server which cause Kermit to
always attempt SSL authentication by default. I have turned this off
and restored our app to its former successful functioning by issuing a
"SET FTP AUTOAUTHENTICATION OFF" before we execute an FTP OPEN. Our sys
admin states nothing changed in the installations of Kermit on our
servers.
My questions are:
1. Does my analysis seem correct?
2. Is "SET FTP AUTOAUTHENTICATION OFF" the right (and/or only) way to
stop Kermit from performing SSL authentication by default (without
removing libraries or modifying make files)?
3. How do I identify the library(ies) which, by their existence, cause
Kermit to default to performing SSL authentication?
4. Since no known library changes were made during our upgrade, how
should we have known about this prior to upgrading?
3. Has anyone else found this to be an issue?
Thank you.
Joe